🌎 rns.kin.earth git 🌍

Micron Document

Node / dev / reticulum / commits / f8a5345

Commit f8a53458d65cf7e8dc093315e40e456de6482b34

󰉖 Browse tree at this commit

Parents : 4229837

Author : Mark Qvist <mark@unsigned.io>

Date : 2023-09-21T18:33:14+02:00

Added respond_to_probes option to example config

Changes

1 files changed, 13 insertions(+), 1 deletions(-)

M RNS/Utilities/rnsd.py +13 -1

Diff

diff --git a/RNS/Utilities/rnsd.py b/RNS/Utilities/rnsd.py

index c170af47..dfde1225 100755

--- a/RNS/Utilities/rnsd.py

+++ b/RNS/Utilities/rnsd.py

@@ -87,7 +87,7 @@ __example_rns_config__ = '''# This is an example Reticulum config file.

# always-on. This directive is optional and can be removed

# for brevity.

-enable_transport = False

+enable_transport = No

# By default, the first program to launch the Reticulum

@@ -111,6 +111,7 @@ share_instance = Yes

shared_instance_port = 37428

instance_control_port = 37429

# You can configure Reticulum to panic and forcibly close

# if an unrecoverable interface error occurs, such as the

# hardware device for an interface disappearing. This is

@@ -120,6 +121,17 @@ instance_control_port = 37429

panic_on_interface_error = No

+# When Transport is enabled, it is possible to allow the

+# Transport Instance to respond to probe requests from

+# the rnprobe utility. This can be a useful tool to test

+# connectivity. When this option is enabled, the probe

+# destination will be generated from the Identity of the

+# Transport Instance, and printed to the log at startup.

+# Optional, and disabled by default.

+respond_to_probes = No

[logging]

# Valid log levels are 0 through 7:

# 0: Log only critical information